Creating and Distributing Power BI Apps

Course: Microsoft Power BI Training

Topic: Creating and Distributing Power BI Apps

Course Link: Microsoft Power BI Training – JustAcademy

Demo Link: Register for a Course Demo

JustAcademy Website: Visit JustAcademy

1. Introduction to Power BI Apps

Microsoft Power BI is a business intelligence platform that helps organizations transform data into interactive reports, dashboards, and analytical insights. After creating reports, organizations often need to distribute them to employees, managers, customers, or other authorized users in a convenient and controlled way.

Power BI apps provide a way to package and distribute a curated collection of reports, dashboards, and other supported content to a specific audience. Instead of asking users to find individual reports across a workspace, developers can publish an app that presents relevant content through a more organized experience.

For example, a retail company might create a Sales Analytics app containing sales performance reports, regional dashboards, product analysis, and inventory reports. Sales managers can access the information relevant to their work from one published app.

1.1 What Is a Power BI App?

A Power BI workspace app is a packaged collection of Power BI content published from a workspace and made available to selected users or groups. Users can access the published content according to the permissions configured by the app publisher.

In current Microsoft documentation, this experience is also called a workspace app. Workspace apps are distinct from the newer organizational app items available in Microsoft Fabric.

1.2 Why Are Power BI Apps Useful?

• Distribute related reports and dashboards in one organized experience.
• Provide a consistent way for business users to access approved analytical content.
• Control which users or groups can access the app.
• Present different content to different audiences when required.
• Reduce the need to share individual report links repeatedly.
• Allow publishers to update content and distribute changes to app users.
• Support business reporting for departments such as sales, finance, operations, and marketing.

1.3 Example of a Business App

A company has several Power BI reports:

• Sales Performance Report
• Regional Sales Report
• Product Profitability Report
• Customer Analysis Report
• Monthly Executive Dashboard

Instead of distributing these items individually, the company can package suitable content into a Sales Analytics app. The app can provide a structured navigation experience and make the reports easier for authorized employees to find.

2. Learning Objectives

After completing this topic, learners should be able to:

• Explain the purpose of Power BI apps.
• Understand the difference between workspaces, reports, dashboards, and apps.
• Prepare reports and dashboards before publishing an app.
• Create a workspace app in the Power BI Service.
• Configure app details, navigation, and content.
• Create multiple audiences and control content visibility.
• Distribute apps to users and groups.
• Understand app permissions and semantic model access.
• Publish updates and manage access requests.
• Understand licensing, security, and governance considerations.
• Troubleshoot common publishing and distribution problems.
• Build a practical Power BI app for a business department.

3. Understanding Workspaces, Reports, Dashboards, and Apps

Power BI uses several related components to support content development, analysis, and distribution. Understanding the differences helps users decide where to create content and how to share it.

3.1 Workspace

A workspace is an environment in the Power BI Service where a team can collaborate on content. Depending on permissions and supported features, a workspace can contain reports, semantic models, dashboards, and other Power BI or Fabric items.

3.2 Report

A report is an interactive collection of pages containing charts, cards, tables, slicers, filters, and other visual elements. Reports are designed for detailed exploration and analysis.

3.3 Dashboard

A dashboard is a single-page canvas in the Power BI Service that brings important metrics and supported visual tiles together for monitoring.

3.4 App

An app packages selected content for a specific audience. It offers users an organized way to access approved content without requiring them to work directly in the development workspace.

3.5 How These Components Work Together

Data Sources
     |
     v
Semantic Model
     |
     v
Reports and Dashboards
     |
     v
Power BI Workspace
     |
     v
Create and Configure App
     |
     v
Publish App
     |
     v
Distribute to Authorized Users
     |
     v
Users Explore Published Content

4. Understanding the Power BI Service

The Power BI Service is the online environment where users publish, manage, share, and consume Power BI content. Workspace apps are created and published from the Power BI Service.

4.1 Common Power BI Service Activities

• Open and manage workspaces.
• View reports and dashboards.
• Create and publish workspace apps.
• Manage app audiences and permissions.
• Share content with authorized users.
• Configure supported data refresh settings.
• Monitor access requests and update published content.

4.2 Before Creating an App

Before starting the publishing process, make sure the workspace contains the content that users need. Review the report pages, dashboard tiles, model dependencies, navigation structure, and permissions.

• Check that report titles are descriptive.
• Remove unnecessary draft or duplicate content from the planned app.
• Validate key calculations and report interactions.
• Check whether reports depend on semantic models in other workspaces.
• Determine which users or groups should receive the app.
• Identify whether different groups need different content.

5. Planning a Power BI App

Good app design begins with understanding the audience. An app should organize information around the tasks that users need to complete rather than simply exposing every available report.

5.1 Identify the Business Purpose

Define the main objective of the app. For example, a Finance app might help users monitor revenue, expenditure, profit, and budget variance. A Human Resources app might present workforce size, recruitment, attrition, and training metrics.

5.2 Identify the Audience

Determine who will use the app and what information they need.

5.3 Decide Which Content to Include

Include content that supports the app's purpose. Too many unrelated reports can make navigation confusing and reduce the usefulness of the app.

For example, a Sales Analytics app might include:

• Sales Overview
• Regional Performance
• Product Profitability
• Customer Analysis
• Sales Targets and Variance

5.4 Plan the Navigation

Organize content in a logical order. Put frequently used reports near the top and use names that describe the information users will find inside each report.

6. Preparing the Workspace for App Publishing

The workspace acts as the development and staging area for the app. Changes made to workspace content are not automatically reflected in an already published app; the app publisher generally needs to update the app to distribute the changes.

6.1 Check Workspace Content

1. Open the Power BI Service.
2. Navigate to the workspace that contains the intended reports and dashboards.
3. Review the list of available content.
4. Open each important report and confirm that its visuals and calculations work correctly.
5. Verify that reports connect to the intended semantic models.
6. Review report titles, descriptions, and navigation.
7. Confirm that the content is appropriate for the intended audience.

6.2 Check Dependencies

Reports may depend on semantic models, paginated reports, or other items. If these dependencies are missing from the app or inaccessible to the audience, some report features or dashboard tiles may fail.

• Identify reports that use semantic models in other workspaces.
• Confirm that the intended audience has access to the required semantic models.
• Include relevant reports when publishing dashboards containing report tiles.
• Check drill-through destinations and related report dependencies.
• Review any paginated reports referenced by other reports.

6.3 Validate Data and Security

Before distributing content, confirm that the data is accurate, refresh settings are appropriate, and security rules are working as intended. Hiding a report from app navigation is not a replacement for configuring appropriate data security.

7. Creating a Power BI Workspace App

Creating a workspace app generally involves configuring the app, selecting content, defining audiences, setting access, and publishing the final experience.

7.1 Step 1: Open the Workspace

1. Sign in to the Power BI Service using an authorized account.
2. Open the workspace containing the reports and dashboards.
3. Confirm that you have the necessary permissions to create and publish an app.
4. Select the option to create an app in the workspace.

The exact labels and page layout may change as Microsoft updates the Power BI and Fabric experiences.

7.2 Step 2: Configure App Details

Provide descriptive information about the app. The setup experience can include fields such as:

• App name: A clear name, such as Sales Analytics App.
• Description: A short explanation of the app's purpose.
• Theme or appearance: A suitable visual identity where supported.
• Support link: A link to the appropriate help or support resource, if available.
• Contact information: Details users can use to request assistance.

Example description: “This app provides sales performance reports, regional analysis, product profitability, and monthly sales indicators for authorized business users.”

7.3 Step 3: Configure Advanced Settings

Depending on the available settings and permissions, app publishers may be able to configure options such as allowing authorized users with Build permission to save copies of reports or controlling access to hidden content.

Review each option carefully. Enabling access to hidden content can allow users with direct links to reach items that are hidden from their app navigation, so content visibility should not be treated as a security boundary.

7.4 Step 4: Add Content

Use the app content configuration area to select the reports, dashboards, and other supported items that should appear in the app.

1. Select the option to add content.
2. Choose the relevant items from the workspace.
3. Review the list of selected content.
4. Arrange the items in a logical order.
5. Rename items where the available app configuration allows it.
6. Add supported links to relevant external resources when useful.
7. Check that dependent reports and dashboards are included as required.

7.5 Step 5: Review the Content List

A well-organized app makes it easy for users to identify the report they need. Use clear names rather than generic names such as “Report 1” or “Dashboard 2.”

8. Creating and Managing App Audiences

Audiences allow an app publisher to provide different content experiences to different groups of users. For example, managers may need access to summary and detailed reports, while executives may need only the main KPI reports.

8.1 What Is an App Audience?

An audience is a configured group of users or groups that can access selected app content. Different audiences can have different content visibility and access settings.

8.2 Example Audience Structure

8.3 Steps to Create an Audience

1. Open the app's audience configuration area.
2. Create a new audience.
3. Give the audience a descriptive name, such as Executives.
4. Choose which content items should be visible to that audience.
5. Assign the intended users or groups.
6. Review the access settings for the audience.
7. Repeat the process for additional audiences as needed.
8. Preview or test the configuration before publishing.

Microsoft documentation currently describes support for up to 25 audience groups in a workspace app. Practical limits and available features should be checked against the organization's current Power BI environment.

8.4 Hide and Show Content

Content visibility determines which items appear in an audience's app navigation. Hiding a report from the navigation does not necessarily prevent access through a direct link when hidden-content access is enabled and the user otherwise has the required permissions.

Therefore, use audience settings to organize the app experience and use appropriate permissions and security rules to protect sensitive information.

8.5 Audience Best Practices

• Create audiences based on actual business responsibilities.
• Use meaningful audience names.
• Give each audience only the content it needs.
• Use organizational security groups when suitable and supported.
• Avoid creating unnecessary overlapping audiences.
• Test the app using representative users from each audience.
• Review content visibility whenever the app is updated.

9. Managing App Permissions

Permissions determine who can access the app and what additional activities they can perform. Access to an app, access to a report, and access to an underlying semantic model are related but distinct considerations.

9.1 App Access

App publishers can assign access to specific users or groups and, where permitted by the organization, make an app available to a broader organizational audience.

9.2 Semantic Model Access

App users may also need access to semantic models used by the published content. This is especially important when a report uses a model stored in a different workspace.

9.3 Build Permission

Build permission allows authorized users to create supported content from a semantic model, such as building their own reports. It is different from permission to view an existing report.

9.4 Share Permission

Depending on the app configuration, publisher permissions, and available features, users may be granted the ability to share semantic models or create content based on them. Grant these capabilities only when they match the user's responsibilities.

9.5 Permission Planning Table

10. Publishing a Power BI App

Publishing makes the configured app available to its intended audience. Before publishing, review the app details, selected content, audience membership, content visibility, and permissions.

10.1 Publishing Steps

1. Complete the app setup.
2. Verify that the correct reports, dashboards, and supported content are included.
3. Check each audience's visible content.
4. Review user and group assignments.
5. Verify that underlying semantic model permissions are appropriate.
6. Check that report dependencies are included and accessible.
7. Select the publish option.
8. Wait for the publishing process to complete.
9. Copy the app link when it is provided.
10. Share the link with the intended users through an approved communication channel.

10.2 After Publishing

After successful publishing, test the app as an end user. Confirm that the app opens, the expected items are visible, the reports load, and the users can access the required data.

For internal users, publishing or updating an app does not necessarily send an email notification. A separate communication may be needed to explain the app's availability and provide its link.

11. Distributing Power BI Apps to Users

Distribution is the process of making the published app available to the intended audience. Power BI supports several distribution approaches, subject to the organization's settings and permissions.

11.1 Method 1: Share an App Link

After publishing the app, copy its shareable link and send it to authorized users. Users must still satisfy the required access and licensing conditions.

This method is useful when a department needs a simple way to direct users to a newly published app.

11.2 Method 2: Find the App from the Apps Page

Users may be able to find and install apps from the Apps page in the Power BI Service. The exact navigation experience can vary as Microsoft rolls out interface updates.

11.3 Method 3: Automatically Install an App

Where an administrator has enabled the required setting and granted the necessary permissions, an app publisher may be able to arrange for an app to appear automatically for intended users.

Automatic installation is subject to organizational settings and is not available in every scenario. Publishers should coordinate with the Power BI or Fabric administrator before relying on this method.

11.4 Method 4: Distribute to External Users

External distribution may be possible when the organization and Power BI configuration support it. External users generally require appropriate identity access, permissions, and licensing or capacity arrangements.

Before distributing content externally, review organizational policies, data sensitivity, tenant settings, and the access requirements for the underlying reports and semantic models.

11.5 Choosing a Distribution Method

12. Licensing and Capacity Considerations

Power BI app publishing and consumption depend on the organization's licensing and capacity configuration. Licensing rules can change, so always verify current Microsoft requirements before distributing an app widely.

12.1 Publisher Requirements

Creating or updating workspace apps generally requires a Power BI Pro or Premium Per User (PPU) license and the appropriate workspace permissions, subject to current product rules.

12.2 Consumer Requirements

Users viewing an app may need Pro or PPU licenses when the content is hosted outside qualifying capacity. In supported Power BI Premium or Microsoft Fabric F64-or-higher capacity scenarios, eligible users with free licenses may be able to view content without individual Pro or PPU licenses, subject to the relevant limitations.

12.3 Licensing Checklist

• Check the publisher's license and workspace permissions.
• Identify the capacity hosting the workspace content.
• Verify the license requirements for app consumers.
• Confirm that the app's reports and semantic models have the required permissions.
• Review any licensing restrictions affecting Build permission or report creation.
• Confirm current requirements with the Power BI administrator or official Microsoft documentation.

13. Updating a Published Power BI App

Business requirements change over time. Reports may be improved, new metrics may be added, or some content may need to be removed. The app publisher can make changes in the workspace and publish an update to distribute the revised app.

13.1 Common Reasons for Updating an App

• Adding a new report or dashboard.
• Updating an existing report.
• Changing content order or descriptions.
• Creating a new audience.
• Changing content visibility for an audience.
• Updating access assignments.
• Improving navigation and the user experience.

13.2 Update Procedure

1. Open the workspace associated with the published app.
2. Make the necessary changes to the workspace content.
3. Open the app editing experience.
4. Review the setup, content, and audience configurations.
5. Check the visibility of any newly added content for each audience.
6. Verify user and group access.
7. Select the option to update the app.
8. Wait for the update to complete successfully.
9. Test the published app and communicate important changes to users.

13.3 Important Update Considerations

Changes made in the workspace do not automatically become part of the published app until the app is updated. Newly added content may not be visible to every audience by default, so review audience visibility after adding reports or dashboards.

Removing a report from an app and publishing the change can remove user customizations associated with that report, such as personal bookmarks or comments. Carefully assess the consequences before removing published content.

14. Managing App Access Requests

Users who discover an app but do not have access may be able to request permission, depending on the configuration. App owners or authorized workspace users can review access requests and decide whether to grant access.

14.1 Access Request Workflow

1. A user opens an app link or discovers the app in the Apps page.
2. If access is missing, the user follows the available access request process.
3. The app owner or authorized administrator reviews the request.
4. The request is approved or declined according to organizational policy.
5. If approved, the user is assigned the required access.
6. The user tests the app and confirms that the intended content is available.

14.2 Access Management Best Practices

• Review requests regularly.
• Verify the requester's role and business need.
• Assign users to the correct audience.
• Confirm the required semantic model permissions.
• Use security groups where appropriate.
• Document decisions for sensitive business content.

15. App Security and Data Governance

App distribution should be designed with security and governance in mind. An app's audience settings determine which content is presented to a user, while the relevant permissions and security rules control access to the content and data.

15.1 Row-Level Security

Row-level security (RLS) restricts which rows a user can see in a semantic model. For example, a regional sales manager might be allowed to view only records associated with the manager's region.

RLS should be defined and tested in the semantic model. Hiding a report from an audience is not a substitute for row-level security.

15.2 Least-Privilege Access

The principle of least privilege means giving users only the permissions required for their work. A user who only needs to view reports should not automatically receive permissions to edit workspace content or create new reports.

15.3 Security Checklist

• Review workspace roles and app audience membership.
• Check access to the underlying semantic models.
• Test RLS with representative users.
• Review whether Build and sharing permissions are necessary.
• Understand the effect of enabling access to hidden content.
• Review external access settings before inviting guests.
• Remove access when users no longer need it.
• Follow organizational policies for confidential and sensitive data.

16. App Navigation and User Experience

A well-designed app makes it easy for users to find information and understand what each report contains. The app should have a logical structure and use clear titles and descriptions.

16.1 Navigation Best Practices

• Put frequently used reports near the top of the content list.
• Use concise, descriptive names.
• Group content according to business tasks or responsibilities.
• Remove duplicate or outdated reports from the app.
• Include support information where appropriate.
• Test navigation with users who were not involved in creating the app.

16.2 Example App Navigation

Sales Analytics App
    |
    |-- Sales Overview
    |-- Regional Performance
    |-- Product Profitability
    |-- Customer Analysis
    |-- Sales Targets
    |-- Help and Support

This structure is an example of how an app might organize related sales content. The actual navigation options depend on the items and settings supported by the Power BI app experience.

17. Monitoring and Maintaining Power BI Apps

Publishing an app is not the end of the development process. Reports, semantic models, access requirements, and business definitions may change, so ongoing maintenance is important.

17.1 Maintenance Activities

• Review app usage and user feedback where available.
• Monitor semantic model refresh failures.
• Check whether reports and dashboards still meet business requirements.
• Review audience membership and permissions periodically.
• Test new or updated content before publishing changes.
• Remove outdated content carefully.
• Keep app descriptions and support information up to date.

17.2 Release Management

For business-critical apps, consider a controlled release process. Make changes in a development or staging environment where appropriate, test them, and then publish approved changes to the intended audience.

This process helps reduce the risk of distributing incomplete reports or breaking existing app navigation.

18. Common Problems and Troubleshooting

19. Hands-On Project: Creating a Sales Analytics App

Project Objective: Create and distribute a Power BI app containing sales reports and dashboards for different business audiences.

19.1 Business Scenario

A retail company wants to distribute sales performance information to executives, regional managers, and sales analysts. Each audience needs different levels of detail.

19.2 Required Content

• Sales Overview Report
• Regional Performance Report
• Product Profitability Report
• Customer Analysis Report
• Executive Sales Dashboard

19.3 Step 1: Prepare the Workspace

1. Create or open an appropriate workspace.
2. Publish or create the required reports and dashboards.
3. Validate the semantic model and key DAX measures.
4. Test filters, slicers, and report interactions.
5. Confirm that all required data sources and dependencies are available.

19.4 Step 2: Create the App

1. Open the workspace in the Power BI Service.
2. Select the app creation option.
3. Enter the name Sales Analytics App.
4. Add a description and support details where appropriate.
5. Review available advanced settings.

19.5 Step 3: Add Content

Add the Sales Overview, Regional Performance, Product Profitability, Customer Analysis, and Executive Sales Dashboard items as appropriate. Arrange them in a logical order and verify that related reports are available to the intended audiences.

19.6 Step 4: Configure Audiences

19.7 Step 5: Review Permissions

• Assign the correct users or groups to each audience.
• Check access to the underlying semantic models.
• Review Build and sharing permissions.
• Test any required RLS roles.
• Confirm that restricted content is not exposed to unintended users.

19.8 Step 6: Publish and Distribute

1. Publish the app.
2. Copy the app link.
3. Distribute it to the intended users using an approved method.
4. Provide brief instructions on how to open the app and navigate its reports.
5. Test access with representative users from each audience.

19.9 Step 7: Maintain the App

Gather user feedback, monitor data refresh, correct report issues, and update the app whenever content or audience requirements change.

20. Hands-On Exercises

Exercise 1: Understand the App Structure

Identify the workspace, reports, dashboards, semantic models, and intended app audience in a sample Power BI solution.

Exercise 2: Create a Workspace App

Use a workspace containing at least two reports. Configure the app name, description, content order, and support information, then publish the app in an authorized environment.

Exercise 3: Create Multiple Audiences

Create separate audiences for managers and analysts. Configure different content visibility and test the experience using suitable accounts or approved test arrangements.

Exercise 4: Distribute an App

Copy the published app link and share it with authorized test users. Verify that each user can access the correct content.

Exercise 5: Update a Published App

Add a new report to the workspace, update the app, review audience visibility, and confirm that the new report appears for the intended users.

Exercise 6: Audit App Permissions

Review app audiences, semantic model access, Build permissions, and RLS. Document any permissions that should be changed before the app is distributed more widely.

21. Interview Questions and Answers

Q1. What is a Power BI app?

A Power BI workspace app is a packaged collection of reports, dashboards, and other supported content published from a workspace for an intended audience.

Q2. Why are Power BI apps used?

They provide an organized way to distribute related analytical content to business users while managing content visibility and access.

Q3. Where are workspace apps created?

Workspace apps are created and published through the Power BI Service from a suitable workspace.

Q4. What is the difference between a workspace and an app?

A workspace is primarily a collaborative environment for creating and managing content. An app is a curated published experience for users to consume selected content.

Q5. What is the difference between a report and an app?

A report is an interactive analytical document. An app packages one or more reports and other supported items for distribution.

Q6. What is an app audience?

An audience is a configured group of users or groups that can access selected app content.

Q7. Can different audiences see different reports?

Yes. Publishers can configure content visibility for different audiences within a workspace app.

Q8. How do you publish a Power BI app?

Configure the app, add content, define audiences and access, review the settings, and select the publish option.

Q9. How can a published app be distributed?

Depending on the configuration, users can receive a direct app link, find the app through the Apps page, or receive an app through supported automatic installation.

Q10. What is Build permission?

Build permission allows authorized users to create supported new content, such as reports, using a semantic model.

Q11. Does app access automatically guarantee access to every semantic model?

No. Users may need appropriate permissions on underlying semantic models, especially when those models are stored in different workspaces.

Q12. What happens when an app is updated?

The publisher distributes the revised app configuration and content to its users. The publisher should review content visibility and permissions before updating.

Q13. Why might newly added content not appear in an app?

The content may not have been included in the app update or may be hidden from the relevant audience.

Q14. Is hiding content the same as securing it?

No. Hiding content controls the app navigation experience. Permissions and model security must be configured separately to protect data and content.

Q15. What is row-level security?

Row-level security restricts which rows of data a user can access based on configured security rules in the semantic model.

Q16. Why should an app publisher test audience access?

Testing helps confirm that users can see the correct content and that the app does not expose information beyond their authorized access.

Q17. Can an app include content from different reports?

Yes. A workspace app can package multiple supported content items from the workspace, subject to app configuration and dependency requirements.

Q18. What should be checked before distributing an app externally?

Review identity access, guest settings, organizational policies, permissions, data sensitivity, and licensing or capacity requirements.

Q19. What license is generally required to publish or update a workspace app?

Publishing or updating generally requires Power BI Pro or Premium Per User, along with appropriate permissions, subject to current product requirements.

Q20. How can a Power BI app be maintained effectively?

Monitor refresh and access, gather user feedback, validate content changes, review audience permissions, and publish tested updates.

22. Quick Revision Checklist

• Understand the purpose of a Power BI workspace app.
• Differentiate workspaces, semantic models, reports, dashboards, and apps.
• Prepare and validate workspace content before publishing.
• Configure app name, description, support information, and content.
• Organize content in a logical navigation order.
• Create audiences based on business responsibilities.
• Control which content is visible to each audience.
• Review app, report, and semantic model permissions.
• Understand Build permission and row-level security.
• Publish the app and distribute its link appropriately.
• Check licensing and capacity requirements.
• Update the app when reports or audience needs change.
• Review access requests and remove unnecessary access.
• Test the published app as an end user.
• Maintain documentation and follow organizational governance policies.

23. Conclusion

Creating and distributing Power BI apps is an important skill for delivering business intelligence content to the right people. Workspace apps help organizations package related reports, dashboards, and other supported items into a curated experience.

A successful app requires more than publishing a collection of reports. It also requires thoughtful content organization, audience planning, correct permissions, reliable semantic models, suitable licensing, and ongoing maintenance.

By preparing workspace content, configuring audiences, publishing carefully, and testing access, Power BI developers can provide a more organized and secure reporting experience for business users.

24. Additional Learning Resources

• Microsoft Learn: Create and Distribute Power BI Workspace Apps
• Microsoft Learn: Workspaces in Power BI
• Microsoft Learn: Understand Power BI Semantic Models
• Microsoft Learn: Row-Level Security
• Microsoft Learn: Power BI Licenses and Features
• Explore Microsoft Power BI Training at JustAcademy
• Register for a Course Demo
• Visit JustAcademy